Refer to the Common Syntax Options section in this chapter for information about formatting the output of bulk statistics.
Important: Unless otherwise indicated, all statistics are counters. For statistics with the Int32 data type, the roll-over to zero limit is 4,294,967,295. For statistics with the Int64 data type, the roll-over to zero limit is 18,446,744,073,709,551,615.
Variables within the format string must be enclosed within “% and %”, for example, “%var%”. The actual variables supported are command-dependent and are described in the Statistics and Counters Reference.
For a list of the statistics that are common to all schema, refer to the Statistics and Counters Reference.
no aal2 schema schema_name
format format_string
Specifies the schema format as an alphanumeric string of 1 through 3599 characters. For syntax details, see the Schema Format String Syntax section.
Important: For a complete list of the statistics that are supported for this schema, refer to the Statistics and Counters Reference.Use this command to define schemas for ATM adaptation layer 2 (AAL2) bulk statistics collection. Multiple AAL2 schemas can be created to further categorize HNB-GW-level bulk statistics. All of the schemas are processed at each collection interval. To create multiple AAL2 schemas, re-issue the aal2 schema schema_name command using a different schema name.
The following command creates a schema called aal2stats1 that records the number of AAL2 uplink packets transmitted and AAL2 downlink packets received by Access Link Control Application Part (ALCAP) service on HNB-GW:
no alcap schema schema_name
format format_string
Specifies the schema format as an alphanumeric string of 1 through 3599 characters. For syntax details, see Schema Format String Syntax section.
Important: For a complete list of the statistics that are supported for this schema, refer to the Statistics and Counters Reference.Use this command to define schemas for Access Link Control Application Part (ALCAP) service bulk statistics collection on HNB-GW node. Multiple ALCAP schemas can be created to further categorize at AAL2 channel-level bulk statistics. All of the schemas are processed at each collection interval. To create multiple ALCAP schemas, re-issue the alcap schema schema_name command using a different schema name.
The following command creates a schema called alcap1stats1 that records the number of AAL2 channels in connecting and connected state on ALCAP service:
no apn schema schema_name
format format_string
Specifies the schema format as an alphanumeric string of 1 through 3599 characters. For syntax details, see Schema Format String Syntax section.
Important: For a complete list of the statistics that are supported for this schema, refer to the Statistics and Counters Reference.Use this command to define schemas for APN bulk statistics collection. Multiple APN schemas can be created to further categorize APN-level bulk statistics. All of the schemas are processed at each collection interval. To create multiple APN schemas, re-issue the apn schema schema_name command using a different schema name.
The following command creates a schema called apn1stats1 that records the number of sessions currently facilitated by the APN:
no asngw schema schema_name
format format_string
Specifies the schema format. as an alphanumeric string of 1 through 3599 characters. For syntax details, see Schema Format String Syntax section.
Important: For a complete list of the statistics that are supported for this schema, refer to the Statistics and Counters Reference.Use this command to define schemas for ASN-GW bulk statistics collection. Multiple ASN-GW service schemas can be created to further categorize ASN-GW service bulk statistics. All of the schemas are processed at each collection interval. To create multiple ASN-GW service schemas, re-issue the asngw schema schema_name command using a different schema name.
To create an ASN-GW schema called asngw_statistics that specifies a schema format of:
|
•
|
VPN context name: vpnname
|
|
•
|
VPN Context Identifier: vpnid
|
|
•
|
ASN-GW Service name: servname
|
|
•
|
ASN-GW Service identifier: servid
|
|
•
|
Peer IP address: peeripaddr
|
no bcmcs schema schema_name
format format_string
Specifies the schema format as an alphanumeric string of 1 through 3599 characters. For syntax details, see Schema Format String Syntax section.
Important: For a complete list of the statistics that are supported for this schema, refer to the Statistics and Counters Reference.Use this command to define schemas for BCMCS bulk statistics collection. Multiple BCMCS schemas can be created to further categorize BCMCS-level bulk statistics. All of the schemas are processed at each collection interval. To create multiple BCMCS schemas, re-issue the bcmcs schema schema_name command using a different schema name.
The following command creates a schema named bcmcs1stats1 that records the number of sessions currently facilitated by BCMCS:
no card schema schema_name
format format_string
Specifies the schema format as an alphanumeric string of 1 through 3599 characters. For syntax details, see Schema Format String Syntax section.
Important: For a complete list of the statistics that are supported for this schema, refer to the Statistics and Counters Reference.Use this command to define schemas for card bulk statistics collection. Multiple card schemas can be created to categorize card-level bulk statistics. All of the schemas are processed at each collection interval. To create multiple card schemas, re-issue the card schema schema_name command using a different schema name.
Important: Not supported on all platformsThe following command creates a schema called card1stats1 that records the number of processes for all installed cards:
To create a card-level schema called cardresourcestats that specifies a schema format of:
|
•
|
Chassis slot number: slot
|
|
•
|
|
•
|
Available CPU (%): cpuidle
|
no context schema schema_name
format format_string
Specifies the schema forma as an alphanumeric string of 1 through 3600 characters. For syntax details, see Schema Format String Syntax section.
Important: For the complete list of the statistics that are supported for this schema, refer to the Statistics and Counters Reference.Use this command to define schemas for Context bulk statistics collection. Multiple context schemas can be created to categorize context statistics. All of the schemas are processed at each collection interval. To create multiple context schemas, re-issue the context schema schema_name command using a different schema name.
To create a Firewall context schema called sfw_context_stats1 that specifies a schema format of:
|
•
|
Total packets received by firewall: sfw-total-rxpackets
|
|
•
|
Total packets sent by firewall: sfw-total-txpackets
|
|
•
|
Total ICMP packets discarded by firewall: fw-icmp-discardpackets
|
no cscf schema schema_name
format format_string
Specifies the schema format. as an alphanumeric string of 1 through 3599 characters. For syntax details, see Schema Format String Syntax section.
Important: For a complete list of the statistics that are supported for this schema, refer to the Statistics and Counters Reference.Use this command to define schemas for CSCF bulk statistics collection. Multiple CSCF-service schemas can be created to categorize CSCF-service bulk statistics. All of the schemas are processed at each collection interval. To create multiple CSCF-service schemas, re-issue the cscf schema schema_name command using a different schema name.
To create a CSCF schema called cscf_statistics that specifies a schema format of:
|
•
|
Call attempts received: callattrx
|
|
•
|
Call attempts transmitted: callatttx
|
|
•
|
Call successes received: callsuccrx
|
|
•
|
Call successes transmitted: callsucctx
|
|
•
|
Call failures received: callfailrx
|
|
•
|
Call failures transmitted: callfailtx
|
no cs-network-ranap schema schema_name
format format_string
Specifies the schema format as an alphanumeric string of 1 through 3599 characters. For syntax details, see Schema Format String Syntax section.
Important: For a complete list of the statistics that are supported for this schema, refer to the Statistics and Counters Reference.Use this command to define schemas for RANAP procedure related bulk statistics collection in a CS network associated with HNB-GW in a Femto UMTS network. Multiple CS Networks RANAP schemas can be created to further categorize at CS network or HNB-GW-level bulk statistics. All of the schemas are processed at each collection interval. To create multiple CS Networks RANAP schemas, re-issue the cs-network-ranap schema schema_name command using a different schema name.
The following command creates a schema called cs_ranap1stats1 that records the total number of Iu Release Request messages transmitted and total number of Iu Release Command message received by the HNB-GW node:
no cs-network-rtp schema schema_name
format format_string
Specifies the schema format as an alphanumeric string of 1 through 3599 characters. For syntax details, see Schema Format String Syntax section.
Important: For a complete list of the statistics that are supported for this schema, refer to the Statistics and Counters Reference.Use this command to define schemas for RTP procedure related bulk statistics collection in a CS network associated with HNB-GW in a Femto UMTS network. Multiple CS Networks RTP schemas can be created to further categorize at CS network or HNB-GW-level bulk statistics. All of the schemas are processed at each collection interval. To create multiple CS Networks RTP schemas, re-issue the cs-network-rtp schema schema_name command using a different schema name.
The following command creates a schema called cs_rtp1stats1 that records the total number of RTP Downlink Packets received and RTP Uplink Packets transmitted by HNB-GW node in an associated CS network:
no dcca schema schema_name
format format_string
Specifies the schema format as an alphanumeric string of 1 through 3599 characters. For syntax details, see Schema Format String Syntax section.
Important: For a complete list of the statistics that are supported for this schema, refer to the Statistics and Counters Reference.no diameter-acct schema schema_name
format format_string
Specifies the schema format as an alphanumeric string of 1 through 3599 characters. For syntax details, see Schema Format String Syntax section.
Important: For a complete list of the statistics that are supported for this schema, refer to the Statistics and Counters Reference.no diameter-auth schema schema_name
format format_string
Specifies the schema format as an alphanumeric string of 1 through 3599 characters. For syntax details, see Schema Format String Syntax section.
Important: For a complete list of the statistics that are supported for this schema, refer to the Statistics and Counters Reference.no dlci-util schema dlci_schema_name
format dlci_schema_format
Specifies the format of the collected DLCI utilization statistics by identifying the statistics variables and ordering the variables for presentation within the bulk statistics messages. The format value comprises an alphanumeric string of 1 through 3599 characters. For syntax details, see the Schema Format String Syntax section.
Important: For a complete list of the statistics that are supported for the DLCI-Util schema, refer to the Statistics and Counters Reference.Multiple schemas can be created to categorize DLCI-Util bulk statistics. All of the schemas are processed at each collection interval. To create multiple DLCI-Util schemas, re-issue the dlci-util schema dlci_schema_name command using a different schema name each time.
Include the bulk statistic variable names to create a schema named dlciutilstats_sgsn1 that specifies collection of statistics (a schema format) for:
|
•
|
|
•
|
|
•
|
|
•
|
|
•
|
no dpca schema schema_name
format format_string
Specifies the schema format as an alphanumeric string of 1 through 3599 characters. For syntax details, see Schema Format String Syntax section.
Important: For a complete list of the statistics that are supported for this schema, refer to the Statistics and Counters Reference.no ecs schema schema_name
format format_string
Specifies the schema format as an alphanumeric string of 1 through 3599 characters. For syntax details, see Schema Format String Syntax section.
Important: For a complete list of the statistics that are supported for this schema, refer to the Statistics and Counters Reference.Use this command to define schemas for ECS bulk statistics collection. Multiple ECS schemas can be created to categorize ECS bulk statistics. All of the schemas are processed at each collection interval. To create multiple ECS schemas, re-issue the ecs schema schema_name command using a different schema name.
no egtpc schema schema_name
format format_string
Specifies the schema format as an alphanumeric string of 1 through 3599 characters. For syntax details, see Schema Format String Syntax section.
Important: For a complete list of the statistics that are supported for this schema, refer to the Statistics and Counters Reference.Use this command to define schemas for enhanced GTP-C bulk statistics collection. Multiple eGTP-C service schemas can be created to categorize eGTP-C service bulk statistics. All of the schemas are processed at each collection interval. To create multiple eGTP-C service schemas, re-issue the egtpc schema schema_name command using a different schema name.
For an eGTP-C-level schema called egtpcservicestats that specifies a schema format of:
|
•
|
Tunnel - Create Session Request Sent: tun-sent-cresess
|
|
•
|
Tunnel - Create Session Request Received: tun-recv-cresess
|
no fa schema schema_name
format format_string
Specifies the schema format as an alphanumeric string of 1 through 3599 characters. For syntax details, see Schema Format String Syntax section.
Important: For a complete list of the statistics that are supported for this schema, refer to the Statistics and Counters Reference.Use this command to define schemas for FA bulk statistics collection. Multiple FA service schemas can be created to categorize FA service bulk statistics. All of the schemas are processed at each collection interval. To create multiple FA service schemas, re-issue the fa schema schema_name command using a different schema name.
To create a FA-level schema named faservicestats that separates the date, time, and vpnname by tabs, enter the following command:
[ no ] file number
Executing this command allows you to enter the Bulk Statistics File Configuration Mode. This mode supports all of the commands from the Bulk Statistics Configuration mode except limit, local-directory, sample-interval, and transfer-interval. (these commands are configured globally for all “files”.)
Important: Use of bulk statistics “files” is optional. If you do not wish to configure bulk statistic “files”, you can perform a standard configuration using the commands in the Bulk Statistic Configuration Mode. Note, however, that the system logically assigns “file 1” to the standard configuration. Therefore, if you wish to configure bulk statistics “files” at a later time, “file 1” will already be used.
Caution: If the Web Element Manager application is used to collect and process (XML parsing, graphing, etc.) bulk statistics data, “file 1” is used by the Web Element Manager’s default bulk statistics collection information and schemas. To avoid errors in processing by the Web Element Manager, do not configure "file 1" via the CLI. However, it is possible to configure files 1 through 4 using the system’s CLI, regardless of whether or not the Web Element Manager is configured as a receiver. In this case, the bulk statistics data is written to the server but not processed by the Web Element Manager application.no fng schema schema_name
format format_string
Specifies the schema format as an alphanumeric string of 1 through 3599 characters. For syntax details, see Schema Format String Syntax section.
Important: For a complete list of the statistics that are supported for this schema, refer to the Statistics and Counters Reference.footer format format_string
format format_string
Specifies the footer format string for use in generated data files as an alphanumeric string from 1 through 2047 characters. The format string syntax is described in the Schema Format String Syntax section. Default: ““ (an empty footer)
footer Command Format String Variables
Use this command to configure a system to either gather or not gather statistics when the system is in the standby state. This is useful for systems configured for Interchassis Session Recovery (ICSR). See the System Administration Guide for more details on this feature.
no gprs schema gprs_schema_name
format gprs_schema_format
Specifies the format of the collected GPRS statistics by identifying the statistics variables and ordering the variables for presentation within the bulk statistics messages. The format value comprises an alphanumeric string of 1 through 3599 characters. For syntax details, see the Schema Format String Syntax section.
Important: For a complete list of the statistics that are supported for the GPRS schema, refer to the Statistics and Counters Reference.Multiple GPRS schemas can be created to categorize GPRS bulk statistics. All of the schemas are processed at each collection interval. To create multiple GPRS schemas, re-issue the gprs schema gprs_schema_name command using a different schema name each time.
Include the bulk statistic variable names to create a GPRS schema named gprsstats_sgsn1 that specifies collection of statistics (a schema format) for:
no gtpc schema gtpc_schema_name
format gtpc_schema_format
Specifies the schema format as an alphanumeric string of 1 through 3599 characters. For syntax details, see Schema Format String Syntax section.
Important: For a complete list of the statistics that are supported for this schema, refer to the Statistics and Counters Reference.Use this command to define schemas for GTPC bulk statistics collection. Multiple GTPC schemas can be created to categorize GTPC bulk statistics. All of the schemas are processed at each collection interval. To create multiple GTPC schemas, re-issue the gtpc schema schema_name command using a different schema name.
To create a GTPC-level schema named gtpc_stats that specifies a schema format of:
|
•
|
Context Name: vpnname
|
|
•
|
GGSN Service Name: servname
|
|
•
|
Total PDP Contexts Processed: setup-total
|
no gtpp schema gtpp_schema_name
format gtpp_schema_format
Specifies the schema format as an alphanumeric string of 1 through 3599 characters. For syntax details, see Schema Format String Syntax section.
Important: For a complete list of the statistics that are supported for this schema, refer to the Statistics and Counters Reference.Use this command to define schemas for GTPP bulk statistics collection. Multiple GTPP schemas can be created to categorize GTPP bulk statistics. All of the schemas are processed at each collection interval. To create multiple GTPP schemas, re-issue the gtpp schema schema_name command using a different schema name.
To create a GTPP schema named gtpp_statistics that specifies a schema format of:
|
•
|
Time: time
|
|
•
|
Total Redirection Requests Received: redir-rcvd
|
no gtpu schema schema_name
format format_string
Specifies the format of the collected GTP-U statistics by identifying the statistics variables and ordering the variables for presentation within the bulk statistics messages. The format value comprises an alphanumeric string of 1 through 3599 characters.The format string syntax is described by Schema Format String Syntax .
Important: For a complete list of the statistics that are supported for this schema, refer to the Statistics and Counters Reference.Multiple GTP-U schemas can be created to categorize GTP-U bulk statistics. All of the schemas are processed at each collection interval. To create multiple GTP-U schemas, re-issue the gtpu schema schema_name command using a different schema name each time.
no ha schema schema_name
format format_string
Specifies the schema format. as an alphanumeric string of 1 through 3599 characters. For syntax details, see Schema Format String Syntax section.
Important: For a complete list of the statistics that are supported for this schema, refer to the Statistics and Counters Reference.Use this command to define schemas for HA bulk statistics collection. Multiple HA service schemas can be created to categorize HA service bulk statistics. All of the schemas are processed at each collection interval. To create multiple HA service schemas, re-issue the ha schema schema_name command using a different schema name.
For an HA schema named haservicestats that specifies a schema format of:
|
•
|
Number of HA authentication failures: reply-haauthfail
|
|
•
|
Number of Mobile Node authentication failures: reply-mnauthfail
|
header format format_string
format format_string
Specifies the header format string for use in generated data files as an alphanumeric string of 1 through 2047 characters. The format string syntax is described in the Schema Format String Syntax section. Default: ““ (an empty header)
header Command Format String Variables
no hnbgw-hnbap schema schema_name
format format_string
Specifies a name for HNB-AP schema format followed by schema variables. format_string must be an alphanumeric string of 1 through 3599 characters. For syntax details, see the Schema Format String Syntax section.
Important: For a complete list of the statistics that are supported for this schema, refer to the Statistics and Counters Reference.This command defines schemas used for HNB-AP statistics collection. Multiple HNB-AP schemas can be created to further categorize bulk statistics. All of the schemas are processed at each collection interval. To create multiple schemas, re-issue the hnbgw-hnbap schema schema_name command using a different schema name.
The following command creates a schema called hnbap1stats1 that records the number of registered UEs and registered HNBs along with Context name, Context Id, and HNB-GW service name:
To create a schema called hnbapuestats that specifies a schema format of:
|
•
|
Number of UEs with CS and PS Core Network Connections: ue-with-ps-cs-conn
|
|
•
|
Number of UEs in Idle Condition: idle-ue
|
no hnbgw-ranap schema schema_name
format format_string
Specifies a name for RANAP schema format, to be used, followed by schema variables. format_string must be an alphanumeric string of 1 through 3599 characters. For syntax details, see Schema Format String Syntax section.
Important: For a complete list of the statistics that are supported for this schema, refer to the Statistics and Counters Reference.This command defines schemas used for RANAP messaging statistics collection. Multiple RANAP schemas can be created to further categorize bulk statistics. All of the schemas are processed at each collection interval. To create multiple schemas, re-issue the hnbgw-ranap schem schema_name command using a different schema name.
The following command creates a schema called ranap1stats1 that records the number of CS-Direct-Transfer messages sent and received on RANAP along with Context name, Context Id, and HNB-GW service name:
To create a schema called ranappagingstats that specifies a schema format of:
|
•
|
|
•
|
no hnbgw-rtp schema schema_name
Specifies a name for the RTP schema to be used as an alphanumeric string of 1 through 31 characters.
format format_string
Specifies a name for RTP schema format, to be used, followed by schema variables. format_string must be an alphanumeric string of 1 through 3599 characters. For syntax details, see Schema Format String Syntax section.
Important: For a complete list of the statistics that are supported for this schema, refer to the Statistics and Counters Reference.This command defines schemas used for RTP messaging statistics collection. Multiple RTP schemas can be created to further categorize bulk statistics. All of the schemas are processed at each collection interval. To create multiple schemas, re-issue the hnbgw-rtp schema schema_name command using a different schema name.
The following command creates a schema called rtp1stats1 that records the number of RTP uplink packets dropped and number of RTCP application report messages received on RTP link along with Context name, Context Id, and HNB-GW service name:
no hnbgw-rua schema schema_name
Specifies a name for the RUA schema to be used as an alphanumeric string of 1 through 31 characters.
format format_string
Specifies a name for RUA schema format, to be used, followed by schema variables. format_string must be an alphanumeric string of 1 through 3599 characters. For syntax details, see Schema Format String Syntax section.
Important: For a complete list of the statistics that are supported for this schema, refer to the Statistics and Counters Reference.This command defines schemas used for RUA protocol messaging statistics collection. Multiple RUA schemas can be created to further categorize bulk statistics. All of the schemas are processed at each collection interval. To create multiple schemas, re-issue the hnbgw-rua schema schema_name command using a different schema name.
The following command creates a schema called rua1stats1 that records the number of CS-Connect messages received and sent on RUA link along with Context name, Context Id, and HNB-GW service name:
no hnbgw-sctp schema schema_name
format format_string
Specifies a name for SCTP schema format, to be used, followed by schema variables. format_string must be an alphanumeric string of 1 through 3599 characters. For syntax details, see Schema Format String Syntax section.
Important: For a complete list of the statistics that are supported for this schema, refer to the Statistics and Counters Reference.This command defines schemas used for SCTP protocol messaging statistics collection. Multiple SCTP schemas can be created to further categorize bulk statistics. All of the schemas are processed at each collection interval. To create multiple schemas, re-issue the hnbgw-sctp schema schema_name command using a different schema name.
The following command creates a schema called sctp1stats1 that records the number of bytes received from lower layer and number of bytes sent to lower layer over SCTP connection along with Context name, Context Id, and HNB-GW service name:
no hsgw schema schema_name
format format_string
Specifies the format of the collected HSGW statistics by identifying the statistics variables and ordering the variables for presentation within the bulk statistics messages. The format value comprises an alphanumeric string of 1 through 3599 characters.The format string syntax is described by Schema Format String Syntax .
Important: For a complete list of the statistics that are supported for this schema, refer to the Statistics and Counters Reference.Multiple HSGW schemas can be created to categorize HSGW bulk statistics. All of the schemas are processed at each collection interval. To create multiple HSGW schemas, re-issue the hsgw schema schema_name command using a different schema name each time.
no imsa schema schema_name
format format_string
Specifies the format of the collected IMSA statistics by identifying the statistics variables and ordering the variables for presentation within the bulk statistics messages. The format value comprises an alphanumeric string of 1 through 3599 characters.The format string syntax is described by Schema Format String Syntax .
Important: For a complete list of the statistics that are supported for this schema, refer to the Statistics and Counters Reference.Multiple IMSA schemas can be created to categorize IMSA bulk statistics. All of the schemas are processed at each collection interval. To create multiple IMSA schemas, re-issue the imsa schema schema_name command using a different schema name each time.
no ippool schema schema_name
format format_string
Specifies the schema format as an alphanumeric string of 1 through 3599 characters. For syntax details, see Schema Format String Syntax section.
Important: For a complete list of the statistics that are supported for this schema, refer to the Statistics and Counters Reference.Use this command to define schemas for IP pool bulk statistics collection. Multiple IP pool schemas can be created to further categorize IP pool bulk statistics. All of the schemas are processed at each collection interval. To create multiple IP pool schemas, re-issue the ippool schema schema_name command using a different schema name.
To create an IP pool schema named ippoolstats that specifies a schema format of:
|
•
|
no ipsg schema schema_name
format format_string
Specifies the schema format as an alphanumeric string of 1 through 3599 characters. For syntax details, see Schema Format String Syntax section.
Important: For a complete list of the statistics that are supported for this schema, refer to the Statistics and Counters Reference.Use this command to define the schemas used for IPSG bulk statistics collection. Multiple IPSG schemas can be created to categorize IPSG bulk statistics. All of the schemas are processed at each collection interval. To create multiple schemas, re-issue the ipsg schema schema_name command using a different schema name.
To create an IPSG schema named ipsgstats that specifies a schema format of:
|
•
|
Context name: vpnname
|
|
•
|
Service name: servname
|
|
•
|
Total responses sent: total-rsp-sent
|
no lac schema schema_name
format format_string
Specifies the schema format as an alphanumeric string of 1 through 3599 characters. For syntax details, see Schema Format String Syntax section.
Important: For a complete list of the statistics that are supported for this schema, refer to the Statistics and Counters Reference.Use this command to define schemas for LAC bulk statistics collection. Multiple LAC schemas can be created to categorize LAC bulk statistics. All of the schemas are processed at each collection interval. To create multiple schemas, re-issue the lac schema schema_name command using a different schema name.
The following command creates a schema called lac1stats1 that records the number of active subscriber sessions and the number of sessions that failed or were disconnected due to the maximum tunnel limit being reached:
To create a schema called lacresourcestats that specifies a schema format of:
|
•
|
Number of Successful Session Connections: sess-successful
|
|
•
|
Number of Session Attempts That Failed: sess-failed
|
|
•
|
Number of Sessions Currently Active: sess-curative
|
limit kilobytes
Caution: Bulk statistics are stored in Random Access Memory (RAM) on the SMC. In the event of power loss or system failure, the statistics will be lost. If the maximum storage limit has been reached before the system's configured transfer-interval is reached, the oldest information stored in the collection will be overwritten.no lma schema schema_name
format format_string
Specifies the schema format as an alphanumeric string of 1 through 3599 characters. For syntax details, see Schema Format String Syntax section.
Important: For a complete list of the statistics that are supported for this schema, refer to the Statistics and Counters Reference.Use this command to define schemas for LMA bulk statistics collection. Multiple LMA service schemas can be created to categorize LMA service bulk statistics. All of the schemas are processed at each collection interval. To create multiple LMA service schemas, re-issue the lma schema schema_name command using a different schema name.
For an LMA-level schema called lmaservicestats that specifies a schema format of:
|
•
|
Binding Update Received: bindupd
|
|
•
|
Binding Update Received - Denied: bindupd-denied
|
no lns schema schema_name
format format_string
Specifies the format of the collected LNS statistics by identifying the statistics variables and ordering the variables for presentation within the bulk statistics messages. The format value comprises an alphanumeric string of 1 through 3599 characters.The format string syntax is described by Schema Format String Syntax .
Important: For a complete list of the statistics that are supported for this schema, refer to the Statistics and Counters Reference.Multiple LNS schemas can be created to categorize LNS bulk statistics. All of the schemas are processed at each collection interval. To create multiple LNS schemas, re-issue the lns schema schema_name command using a different schema name each time.
local-directory pathname
Use this command to designate a directory on a local file system in which collection files with bulkstats information are stored. The directory specified must already exist. Use the Exec Mode command mkdir to create a directory.
To specify that bulkstats collection files are stored in the local directory /flash/bulkstats, enter the following command:
no mag schema schema_name
Specifies the name to use to refer to the schema and associated format string. schema_name must be an alphanumeric string of 1 through 31 characters.
format format_string
Specifies the schema format as an alphanumeric string of 1 through 3599 characters. For syntax details, see Schema Format String Syntax section.
Important: For a complete list of the statistics that are supported for this schema, refer to the Statistics and Counters Reference.Use this command to define schemas for MAG bulk statistics collection. Multiple MAG service schemas can be created to categorize MAG service bulk statistics. All of the schemas are processed at each collection interval. To create multiple MAG service schemas, re-issue the mag schema schema_name command using a different schema name.
For a MAG-level schema called magservicestats that specifies a schema format of:
|
•
|
Binding Update Sent: bindupd
|
|
•
|
no mipv6ha schema schema_name
format format_string
Specifies the schema format as an alphanumeric string of 1 through 3599 characters. For syntax details, see Schema Format String Syntax section.
Important: For a complete list of the statistics that are supported for this schema, refer to the Statistics and Counters Reference.Use this command to define schemas for MIPv6 HA bulk statistics collection. Multiple MIPv6 HA bulk statistics schemas can be created to categorize MIPv6 HA bulk statistics. All of the schemas are processed at each collection interval. To create multiple MIPv6 HA service schemas, re-issue the mipv6ha schema schema_name command using a different schema name.
The following command creates a schema called mipv6haservicestats that records the number of authorization attempt failures due to access rejects from AAA:
no mme schema schema_name
format format_string
Specifies the schema format as an alphanumeric string of 1 through 3599 characters. For syntax details, see Schema Format String Syntax section.
Important: For a complete list of the statistics that are supported for this schema, refer to the Statistics and Counters Reference.Use this command to define schemas for MME bulk statistics collection. Multiple MME bulk statistics schemas can be created to categorize MME bulk statistics. All of the schemas are processed at each collection interval. To create multiple MME service schemas, re-issue the mme schema schema_name command using a different schema name.
The following command creates a schema called mmeservice_s1ap_cfg_transfers that records the total number of S1AP - transmit data - configuration transfers:
no mvs schema schema_name
format format_string
Specifies the schema format as an alphanumeric string of 1 through 3599 characters. For syntax details, see Schema Format String Syntax section.
Important: For a complete list of the statistics that are supported for this schema, refer to the Statistics and Counters Reference.no nat-realm schema schema_name
format format_string
Specifies the schema format as an alphanumeric string of 1 through 3599 characters. For syntax details, see Schema Format String Syntax section.
Important: For a complete list of the statistics that are supported for this schema, refer to the Statistics and Counters Reference.Use this command to define schemas for NAT Realm bulk statistics collection. Multiple NAT realm schemas can be created to further categorize NAT realm level bulk statistics. All of the schemas are processed at each collection interval. To create multiple NAT Realm schemas, re-issue the nat-realm schema schema_name command using a different schema name.
Configures Policy and Charging Control-Application Function (PCC-AF) service bulk statistics schema.
no pcc-af schema schema_name
format format_string
Specifies the schema format as an alphanumeric string of 1 through 3599 characters. For syntax details, see Schema Format String Syntax section.
Important: For a complete list of the statistics that are supported for this schema, refer to the Statistics and Counters Reference.Use this command to define schemas for PCC-AF service bulk statistics collection. Multiple PCC-AF service schemas can be created to categorize PCC-AF service bulk statistics. All of the schemas are processed at each collection interval. To create multiple PCC-AF service schemas, re-issue the pcc-af schema schema_name command using a different schema name.
The following command creates a schema called pcc_af1stats1 that records the total number of Rx STR messages received and total number of Rx AAR Accept messages sent along with Context name, Context Id, and PCC-AF service name:
no pcc-policy schema schema_name
format format_string
Specifies the schema format as an alphanumeric string of 1 through 3599 characters. For syntax details, see Schema Format String Syntax section.
Important: For a complete list of the statistics that are supported for this schema, refer to the Statistics and Counters Reference.Use this command to define schemas for PCC-Policy service bulk statistics collection. Multiple PCC-Policy service schemas can be created to categorize PCC-Policy service bulk statistics. All of the schemas are processed at each collection interval. To create multiple PCC-Policy service schemas, re-issue the pcc-policy schema schema_name command using a different schema name.
The following command creates a schema called pcc_plcy1stats1 that records the total number of Gx messages sent and total number of Gx CCR messages received along with Context name, Context Id, and PCC-Policy service name:
no pcc-sp-endpt schema schema_name
format format_string
Specifies the schema format as an alphanumeric string of 1 through 3599 characters. For syntax details, see Schema Format String Syntax section.
Important: For a complete list of the statistics that are supported for this schema, refer to the Statistics and Counters Reference.Use this command to define schemas for PCC-Sp-Endpoint bulk statistics collection. Multiple PCC-Sp-Endpoint schemas can be created to categorize PCC-Sp-Endpoint bulk statistics. All of the schemas are processed at each collection interval. To create multiple PCC-Sp-Endpoint schemas, re-issue the pcc-sp-endpt schema schema_name command using a different schema name.
The following command creates a schema called pcc_sp1stats1 that records the total number of SPRMgr Sh session close and open requests received from PCCMgr and processed by PCC-Sp-Endpoint along with Context name, Context Id, and PCC-Sp-Endpoint name:
no pcc-service schema schema_name
format format_string
Specifies the schema format as an alphanumeric string of 1 through 3599 characters. For syntax details, see Schema Format String Syntax section.
Important: For a complete list of the statistics that are supported for this schema, refer to the Statistics and Counters Reference.Use this command to define schemas for PCC-Service bulk statistics collection. Multiple PCC-Service schemas can be created to categorize PCC-Service bulk statistics. All of the schemas are processed at each collection interval. To create multiple PCC-Service schemas, re-issue the pcc-service schema schema_name command using a different schema name.
The following command creates a schema called pcc_svc1stats1 that records the total number of Gx and Gy request processed by PCC-Service along with Context name, Context Id, and PCC-Service name:
no pdif schema schema_name
format format_string
Specifies the schema format as an alphanumeric string of 1 through 3600 characters. For syntax details, see Schema Format String Syntax section.
Important: For a complete list of the statistics that are supported for this schema, refer to the Statistics and Counters Reference.Use this command to define schemas for PDIF bulk statistics collection. Multiple PDIF schemas can be created to categorize PDIF bulk statistics. All of the schemas are processed at each collection interval. To create multiple schemas, re-issue the pdif schema schema_name command using a different schema name.
The following command creates a schema called pdifschema1 for the category current active ipv4 sessions:
no pgw schema schema_name
format format_string
Specifies the format of the collected P-GW statistics by identifying the statistics variables and ordering the variables for presentation within the bulk statistics messages. The format value comprises an alphanumeric string of 1 through 3599 characters.The format string syntax is described by Schema Format String Syntax .
Important: For a complete list of the statistics that are supported for this schema, refer to the Statistics and Counters Reference.Multiple P-GW schemas can be created to categorize P-GW bulk statistics. All of the schemas are processed at each collection interval. To create multiple P-GW schemas, re-issue the pgw schema schema_name command using a different schema name each time.
no port schema schema_name
format format_string
Specifies the schema format. as an alphanumeric string of 1 through 3599 characters. For syntax details, see Schema Format String Syntax section.
Important: For a complete list of the statistics that are supported for this schema, refer to the Statistics and Counters Reference.Use this command to define schemas for port bulk statistics collection. Multiple port schemas can be created to categorize port-level bulk statistics. All of the schemas are processed at each collection interval. To create multiple port schemas, re-issue the port schema schema_name command using a different schema name.
Important: The card variable in the Port schema is not supported on all platformsTo create a port-level schema named portstats1 that separates the card/port, bcast_inpackets, and bcast-outpackets variables by hyphens (“-”), enter the following command:
no ppp schema schema_name
format format_string
Specifies the schema format as an alphanumeric string of 1 through 3599 characters. For syntax details, see Schema Format String Syntax section.
Important: For a complete list of the statistics that are supported for this schema, refer to the Statistics and Counters Reference.Use this command to define schemas for point-to-point protocol bulk statistics collection. Multiple PPP-service schemas can be created to categorize PPP-service bulk statistics. All of the schemas are processed at each collection interval. To create multiple PPP-service schemas, re-issue the ppp schema schema_name command using a different schema name.
To create a ppp-level schema named pppstats that specifies a schema format of:
|
•
|
|
•
|
no ps-network-ranap schema schema_name
format format_string
Specifies the schema format. as an alphanumeric string of 1 through 3599 characters. For syntax details, see Schema Format String Syntax section.
Important: For a complete list of the statistics that are supported for this schema, refer to the Statistics and Counters Reference.Use this command to define schemas for RANAP procedure related bulk statistics collection in a PS network associated with HNB-GW in a Femto UMTS network. Multiple PS Networks RANAP schemas can be created to further categorize at PS network or HNB-GW-level bulk statistics. All of the schemas are processed at each collection interval. To create multiple PS Networks RANAP schemas, re-issue the ps-network-ranap schema schema_name command using a different schema name.
The following command creates a schema called ps_ranap1stats1 that records the total number of Iu Release Request messages transmitted and total number of Iu Release Command message received by HNB-GW node:
no radius schema schema_name
format format_string
Specifies the schema format as an alphanumeric string of 1 through 3599 characters. For syntax details, see Schema Format String Syntax section.
Important: For a complete list of the statistics that are supported for this schema, refer to the Statistics and Counters Reference.Use this command to define schemas for RADIUS bulk statistics collection. Multiple RADIUS schemas can be created to categorize RADIUS bulk statistics. All of the schemas are processed at each collection interval. To create multiple RADIUS schemas, re-issue the radius schema schema_name command using a different schema name.
To create a RADIUS schema named radius_statistics that specifies a schema format of:
|
•
|
Server: ipaddr
|
|
•
|
Authentication Requests Sent: auth-req-sent
|
|
•
|
Accounting Requests Sent: acc-req-sent
|
receiver { mode { redundant | secondary-on-failure } | ip_address { primary | secondary } [ mechanism { { { ftp | sftp } login user_name [ encrypted ] password pwd } | tftp } } ] }
no receiver ip_address
Default: secondary-on-failure
redundant: Files are transferred to both the primary and secondary receivers. If either transfer is not currently possible, the file is transferred when possible. The system continues to hold in memory as much data as possible until the data has been successfully transferred to both receivers. Data is only discarded if the in-memory data reaches the configured limit. Refer to the limit command.
secondary-on-failure: Files are transferred to the secondary receiver if the primary receiver fails. In-memory data is erased once the data is transferred to either the primary or secondary receiver. This is the default behavior.
primary: indicates the receiver is the primary receiver of data.
secondary: indicates the receiver is the secondary receiver of data.
ftp login user_name [ encrypted ] password pwd: the FTP protocol shall be used for data file transfer. user_name specifies the user to provide for remote system secure logins and must be an alphanumeric string of 1 through 31 characters. The password to use for remote system authentication is specified as pwd and must be from 1 to 31 characters or 1 to 64 characters if the encrypted keyword is also specified.
sftp login user_name [ encrypted ] password pwd: the SFTP protocol shall be used for data file transfer. user_name specifies the user to provide for remote system secure logins and must be an alphanumeric string of 1 through 31 characters. The password to use for remote system authentication is specified as pwd and must be from 1 to 31 characters or 1 to 64 characters if the encrypted keyword is also specified.
tftp: the TFTP protocol is to be used to transfer files.
The encrypted keyword is intended only for use by the system while saving configuration scripts. The system displays the encrypted keyword in the configuration file as a flag that the variable following the password keyword is the encrypted version of the plain text password. Only the encrypted password is saved as part of the configuration file.
FTP transfer method allows for login which then provides system logging within the enabled FTP logs.
Important: For redundant receivers, configuration changes to the receivers are applied to all existing and all subsequent data sets pending transfer. If no receiver is configured, bulk statistics will be collected and stored on the system until the maximum amount of memory is used; they will not be transferred to the receiver(s). When the storage limit has been reached the oldest information is overwritten. When a receiver is configured for the primary and secondary target, this command will use both receivers as default if no receiver is specified.format format_string
Specifies the naming convention format to use as an alphanumeric string of 1 through 127 characters. The format string syntax is described in the Schema Format String Syntax section. Default: “%date%-%time%”
Important: The remote file naming format should only use static text and bulk statistic variables to avoid any possible file creation issues on the receivers.remote file Command Naming Format Variables
Important: For redundant receivers, the filenames for the output data files are applied when the information is first gathered. If the name format is modified, the change takes effect for the next data set. The current data set name remains unchanged. even if has not yet been transferred.no rp schema schema_name
format format_string
Specifies the schema format as an alphanumeric string of 1 through 3599 characters. For syntax details, see Schema Format String Syntax section.
Important: For a complete list of the statistics that are supported for this schema, refer to the Statistics and Counters Reference.Use this command to define schemas for R-P bulk statistics collection. Multiple PDSN service schemas can be created to categorize PDSN service bulk statistics. All of the schemas are processed at each collection interval. To create multiple PDSN service schemas, re-issue the rp schema schema_name command using a different schema name.
To create an PDSN-level schema called pdsnservicestats that specifies a schema format of:
|
•
|
Date: date
|
|
•
|
Time: time
|
|
•
|
Number of Authentication Denials: deny-auth
|
sample-interval minutes
no sccp schema sccp_schema_name
format sccp_schema_format
Specifies the format of the collected SCCP statistics by identifying the statistics variables and ordering the variables for presentation within the bulk statistics messages. The format value comprises an alphanumeric string of 1 through 3599 characters. For syntax details, see the Schema Format String Syntax section.
Important: For a complete list of the statistics that are supported for the SCCP schema, refer to the Statistics and Counters Reference.Multiple SCCP schemas can be created to categorize SCCP bulk statistics. All of the schemas are processed at each collection interval. To create multiple SCCP schemas, re-issue the sccp schema sccp_schema_name command using a different schema name each time.
Include the bulk statistic variable names to create an SCCP schema named sccpstats11 that specifies collection of statistics (a schema format) for:
no schema schema_name
format format_string
Specifies the schema format as an alphanumeric string of 1 through 3599 characters. For syntax details, see Schema Format String Syntax section.
Important: For a complete list of the statistics that are supported for this schema, refer to the Statistics and Counters Reference.Use this command to define schemas for system-level bulk statistics collection. Multiple schemas can be created to categorize system-level bulk statistics. All of the schemas are processed at each collection interval. To create multiple system schemas, re-issue the schema schema_name command using a different schema name.
The following command creates a schema called systemstats1 that records the number of current Simple IP and the number of current Mobile IP sessions:
To create a system-level schema called bulksysstats that specifies a schema format of:
|
•
|
Number of currently active sessions: sess-curactcall
|
|
•
|
Number of currently dormant sessions: sess-curdormcall
|
no sgs schema schema_name
Specifies the name to use to refer to the schema and associated format string. schema_name must be an alphanumeric string of 1 through 31 characters.
format format_string
Specifies the format of the collected SGs statistics by identifying the statistics variables and ordering the variables for presentation within the bulk statistics messages. The format value comprises an alphanumeric string of 1 through 3599 characters. The format string syntax is described by Schema Format String Syntax .
Important: For a complete list of the statistics that are supported for this schema, refer to the Statistics and Counters Reference.Multiple SGSN schemas can be created to categorize SGSN bulk statistics. All of the schemas are processed at each collection interval. To create multiple SGSN schemas, re-issue the sgs schema sgs_schema_name command using a different schema name each time.
Include the bulk statistic variable names to create an SGs schema named stats_SGs_release that specifies a collection of statistics (a schema format) for the total number of release messages transmitted, retransmitted, and received:
no sgsn schema schema_name
Specifies the name to use to refer to the schema and associated format string. schema_name must be an alphanumeric string of 1 through 31 characters.
format format_string
Specifies the format of the collected SGSN statistics by identifying the statistics variables and ordering the variables for presentation within the bulk statistics messages. The format value comprises an alphanumeric string of 1 through 3599 characters. The format string syntax is described by Schema Format String Syntax .
Important: For a complete list of the statistics that are supported for this schema, refer to the Statistics and Counters Reference.Multiple SGSN schemas can be created to categorize SGSN bulk statistics. All of the schemas are processed at each collection interval. To create multiple SGSN schemas, re-issue the sgsn schema sgsn_schema_name command using a different schema name each time.
Include the bulk statistic variable names to create an SGSN schema named stats_3Gsgsn1 that specifies collection of statistics (a schema format) for the total number of 3G Attaches per LAC/RAC per MCC& MNC:
no sgtp schema schema_name
Specifies a name for a model collection schema for SGTP statistics. schema_name must be an alphanumeric string of 1 through 31 characters.
format format_string
Specifies the format of the collected SGTP statistics by identifying the statistics variables and ordering the variables for presentation within the bulk statistics messages. The format value comprises an alphanumeric string of 1 through 3599 characters.The format string syntax is described by Schema Format String Syntax .
Important: For a complete list of the statistics that are supported for this schema, refer to the Statistics and Counters Reference.Multiple SGTP schemas can be created to categorize SGTP bulk statistics. All of the schemas are processed at each collection interval. To create multiple SGTP schemas, re-issue the sgtp schema sgtp_schema_name command using a different schema name each time.
Include the bulk statistic variable names to create an SGTP schema named sgtpstats_sgsn1 that specifies collection of statistics (a schema format) will be by IuPS service interface and by RNC for the total number of GTP-C Create PDP Context Request messages received.
no sgw schema schema_name
Specifies a name for a model collection schema for S-GW statistics. schema_name must be an alphanumeric string of 1 through 31 characters.
format format_string
Specifies the format of the collected S-GW statistics by identifying the statistics variables and ordering the variables for presentation within the bulk statistics messages. The format value comprises an alphanumeric string of 1 through 3599 characters.The format string syntax is described by Schema Format String Syntax .
Important: For a complete list of the statistics that are supported for this schema, refer to the Statistics and Counters Reference.Multiple S-GW schemas can be created to categorize S-GW bulk statistics. All of the schemas are processed at each collection interval. To create multiple S-GW schemas, re-issue the sgw schema sgw_schema_name command using a different schema name each time.
Include the bulk statistic variable names to create an S-GW schema named sgwstats_sgw1 that specifies collection of statistics (a schema format) will be by S-GW service interface for the total number of currently idle and active UEs.
show variables schema_name
schema_name specifies the name of the schemas available on the system. Following is the list of available schemas in this release.
|
•
|
|
•
|
|
•
|
|
•
|
|
•
|
|
•
|
|
•
|
|
•
|
|
•
|
|
•
|
|
•
|
|
•
|
|
•
|
|
•
|
|
•
|
|
•
|
|
•
|
|
•
|
|
•
|
|
•
|
|
•
|
|
•
|
|
•
|
|
•
|
|
•
|
|
•
|
|
•
|
|
•
|
|
•
|
|
•
|
|
•
|
|
•
|
|
•
|
|
•
|
|
•
|
|
•
|
|
•
|
|
•
|
|
•
|
|
•
|
|
•
|
|
•
|
|
•
|
|
•
|
|
•
|
|
•
|
|
•
|
|
•
|
|
•
|
|
•
|
|
•
|
|
•
|
|
•
|
|
•
|
|
•
|
no ss7link schema schema_name
Specifies the name to use to refer to the schema and associated format string. schema_name must be an alphanumeric string of 1 through 31 characters.
format format_string
Specifies the naming convention format to use. format_string must be an alphanumeric string of 1 through 3599 characters. The format string syntax is described by Schema Format String Syntax .
Important: For a complete list of the statistics that are supported for this schema, refer to the Statistics and Counters Reference.Multiple collection schemas can be created to categorize SS7 link bulk statistics. All of the schemas are processed at each collection interval. To create multiple SS7 link schemas, re-issue the ss7link schema ss7link_schema_name command using a different schema name each time.
The following command creates a schema called ss7lnk1stats1 that records the changeover orders sent and received per linkset and link and per SS7 routing domain:
no ss7rd schema schema_name
schema_name must be an alphanumeric string of 1 to 31 characters.
format format_string
Specifies the format of the collected SS7 routing domain statistics by identifying the statistics variables and the ordering of the variables for presentation within the bulk statistics collection report. The format value comprises an alphanumeric string of 1 through 3599 characters.The format string syntax is described by Schema Format String Syntax .
Important: For a complete list of the statistics that are supported for this schema, refer to the Statistics and Counters Reference.Multiple collection schemas can be created to categorize SS7 routing domain bulk statistics. All of the schemas are processed at each collection interval. To create multiple SS7 routing domain schemas, re-issue the ss7rd schema ss7rd_schema_name command using a different schema name each time.
The following command creates a schema called ss7rd1stats1 that identifies the SS7 routing domain and records the Application Server Process instance in the SS7 routing domain, along with the total number of sent and received SHUTDOWN messages per SS7 routing domain:
transfer-interval minutes
